This development kit has all the information you will need to begin taking advantage of the Display Manger API. The Display Manager 1.0 API was first introduced with the PowerMacs in System 7.1.2 and subsequently shipped in 7.5 and 7.5.1. The Display Manager 2.0 is included in post 7.5.1 systems and is also available as a system extension which is backward compatible to System 7.1. Licensing information for the Display Manager extension is included to make it as easy as possible for developers to create and ship Display Manager aware applications.
What this development kit contains:
Read Me: The document you are now reading.
Display Manager Documentation: A DocViewer document which contains information on the Display Manager 1.0 features and API. This document is the Display Manager chapter of Inside Macintosh: Advanced Color Imaging, and is also available on the Developer CD Series Reference Library CD from the Apple Developer Group.
Display Manager Sample Code: The PlayVideo sample application and the RequestVideo sample code library, will allow developers to explore the Display Manager API by changing bit depth and screen resolution on multisync displays attached to built-in, NuBus, and PCI based video.
Compiler & Runtime Files: New Displays.h and Video.h header files are included with this development kit. You will need to install these new universal header files only if they are newer than the ones inside your development environment. A link library called "DisplayLib" for the Display Manager 2.0 features (the link library "InterfaceLib" contains the Display Manager 1.0 link time entry points) is included for PowerPC application builds. A runtime library called "Display Library" which contains the PowerPC glue code to use the Display Manager 2.0 API is included and must be available to the application at runtime (the glue library "InterfaceLib" in PowerMac ROMs contains the Display Manager 1.0 glue code). To run a PowerPC application which uses the Display Manager 2.0 features, you must have the "Display Library" file within the Code Fragment Manager search path - in the same directory as the application or in the extensions folder. An alternative is to use the MPW MergeFragment command to place the runtime library directly inside your PowerPC application. Note that the MPW MergeFragment tool will only work with standard PowerPC applications in that there can be no other data in the data fork except PEF containers.
If you have any bug reports or comments, please donﾕt hesitate to link or write. You can contact us through the following:
Alink: DEVSUPPORT (provided you have Apple developer support access)
or
Ian Hendry: EWorld/ALink: HENDRY or Internet: hendry@apple.com
Eric3 Anderson: EWorld/ALink: Eric3 or AOL: ERICTHREE
You can also place your comments in the Developer Talk bulletin boards on EWorld, AppleLink, the internet, Compuserve, AOL, or some other public discussion area.
